QRZ! Ham Radio 4/QRZ Ham Radio Callsign Database - Volume 4.iso/digests/infoham/940028.txt

Internet Message Format | 1994-11-13 | 29KB

Date: Wed, 12 Jan 94 02:10:44 PST
From: Info-Hams Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Info-Hams Digest V94 #28
To: Info-Hams


Info-Hams Digest            Wed, 12 Jan 94       Volume 94 : Issue   28

Today's Topics:
                              ans001.03
                              ans001.04
                     ANS Bulletin 001.01 (2 msgs)
                    CA HAM vs Sheriff/FCC Update?
                             Fm Broadcast
                       Ramsey kits not too good

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Info-Hams Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/info-hams".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 12 Jan 94 04:34:27 GMT
From: [e-mail]
Subject: ans001.03
To: [e-mail]

On 6 Jan 1994 [e-mail]. wrote:

> R:940109/0411z 54983@KE7KD.#NONEV.NV.USA.NOAM [RENO, NV.]
> R:940109/0337Z @:F6CNB.#SETX.TX.USA.NA [SugarLand] #:83876 Z:77478
> R:940107/0946Z @:F5KEQ.FPDL.FRA.EU [Nantes] #:77485 Z:44087 FBB5.15-TCP/I=
P
> R:940106/2351Z @:F6KSU.FPDL.FRA.EU [Laval] Z:53000  $:940105031232
> R:940106/2329Z @:F6DEG.FNOR.FRA.EU [Alen=87on] #:241479 Z:61000 FBB5.15
> R:940106/2248Z @:F6RAE.FNOR.FRA.EU [Vernon] #:257041 Z:27207 FBB5.15
> R:940106/2242Z @:F6RAC.FRPA.FRA.EU #:250029 [Paris - FBB5.13]
> R:940106/2223Z @:F6PTT.FRPA.FRA.EU #:64800 [91-MASSY] FBB5.15b $:94010503=
1232
> R:940106/2159Z @:F5MSQ.FCEN.FRA.EU [MUIDES] #:52238 Z:41500 FBB5.15
> R:940106/2130Z @:F8REF.FCEN.FRA.EU [Tours] #:44371 Z:37100 FBB5.15
> R:940106/2122Z @:F6KBN.FCEN.FRA.EU [St EPAIN] #:7991 Z:37320 FBB5.15
> R:940106/2107Z @:F5GHV.FPOC.FRA.EU [Poitiers] #:251558 Z:86000 $:94010503=
1232
> R:940106/2005Z @:F1HAQ.FALI.FRA.EU [Brive] #:280831 Z:JN05SD $:9401050312=
32
> R:940106/2001Z @:F6KDC.FALI.FRA.EU [Clermont-Fd]#:197033 JN15NQ $:9401050=
31232
> R:940106/1955Z @:F6BIG.FRHA.FRA.EU [Annecy (74)] #:399578 Z:74940 FBB5.15
> R:940106/1953Z @:HB9IAP.SROM.CHE.EU [GENEVE] #:232864 Z:1213 FBB5.15-I.A.=
P.C.
> R:940106/1932z @HB9PD.CHE.EU [PRIG BOX Bern, JN36RW, TheBox 1.9b]
> R:940106/0859z @HB9EAS.CHE.EU [The Basel Area BBS]
> R:940106/0902z @DB0GE.#SAR.DEU.EU [BBS Saarbruecken, DieBox 1.9]
> R:940106/0828z @ON4UBO.#LG.BEL.EU [Battice(LG),JO20VP,OP : ON4UAA]
> R:940106/0831Z @:ON1AEO.#DST.BEL.EU [Schaffen] #:11537 Z:3290 FBB5.15
> R:940106/0737Z @:ON6AR.#AN.BEL.EU [Antwerpen <PWG>] #:56441 Z:B-2000 FBB5=
.15
> R:940106/0622Z @:ON4AWP.OVN.BEL.EU [Gent, JO11ub] #:21207 Z:B-9000 FBB5.1=
5
> R:940106/0558Z @:PI8MID.#ZLD.NLD.EU [Middelburg] Z:4336XD $:940105031232
> R:940106/0350Z @:PI8VNW.#ZH2.NLD.EU [Hoek v Holland] #:6041 Op:PE0MAR
> R:940106/0207z @:PA0OKC.AMPR.ORG. [Z'meer] JNOS1.15 #:9841 $:940105031232=
 Z:2724 HR
>=20
> >From [e-mail] Thu Jan 06 02:08:02 1994
> Received: from duttnpc.tn.tudelft.nl by pa0okc.ampr.org. (JNOS1.15) with =
SMTP
> =09id AA9841 ; Thu, 06 Jan 94 02:07:26 UTC
> Received: from amsat.org by duttnpc.tn.tudelft.nl (JNOS1.10x1) with SMTP
> =09id AA20616 ; Wed, 05 Jan 94 04:44:06 UTC
> Received: from localhost by AMSAT.Org (8.6.4/amsat.1)
> =09id DAA04533 to ans-dist; Wed, 5 Jan 1994 03:17:04 GMT
> Received: from dub-img-2.compuserve.com by AMSAT.Org (8.6.4/amsat.1)
> =09id TAA04529 to <[e-mail]>; Tue, 4 Jan 1994 19:17:00 -0800
> Received: from localhost by dub-img-2.compuserve.com (8.6.4/5.930129sam)
> =09id WAA24261; Tue, 4 Jan 1994 22:14:34 -0500
> >From: Russ Platt WJ9F <[e-mail]>
> Message-ID: <[e-mail]>
>=20
> HR AMSAT NEWS SERVICE BULLETIN 001.03 FROM AMSAT HQ
> SILVER SPRING,MD January 1, 1994
> TO ALL RADIO AMATEURS BT
> BID: $ANS-001.03
>=20
> Experimenter's Day Returns to AO-16
>=20
> AO-16 Command Team Leader, Russ Platt, WJ9F, announces the resumption
> of Experimenter's Day on Pacsat.  In the past Experimenter's Days on Pacs=
at
> the procedure was to change to the Pacsat Raised Cosine PSK transmitter
> on 437.050 Mhz and activate the S-Band transmitter on 2400.143 Mhz.  With
> the decline of the carrier suppression on the "Straight" PSK transmitter
> (437.025 Mhz) the RC PSK transmitter has become the primary downlink for=
=20
> some time.  In the upcoming schedule of Experimenter's Days the power out=
put
> will be reduced on the RC PSK transmitter and the S-Band transmitter will
> be turned on.  The power output from the S-Band transmitter is not variab=
le
> so power management is controlled by varying the output of the RC PSK=20
> transmitter. =20
>=20
> Experimenter's Days managed by AMSAT-NA have been held on UTC Wednesdays
> since the days of AMSAT-OSCARS 6 and 7 when Wednesday was " battery recha=
rge
> day." (Incidentally, this is also the reason that the continental U.S.
> 75 meter nets were originally scheduled for Tuesday evenings.)
>=20
> Future Experimenter's Days are scheduled for:
>=20
> 05 January  0411 UTC  through  06 January  0340 UTC
> 26 January  0400 UTC  through  27 January  0330 UTC
>=20
>=20

------------------------------

Date: 12 Jan 94 04:35:21 GMT
From: [e-mail]
Subject: ans001.04
To: [e-mail]

On 6 Jan 1994 [e-mail]. wrote:

> R:940109/0336Z @:F6CNB.#SETX.TX.USA.NA [SugarLand] #:83872 Z:77478
> R:940107/0943Z @:F5KEQ.FPDL.FRA.EU [Nantes] #:77484 Z:44087 FBB5.15-TCP/I=
P
> R:940106/2349Z @:F6KSU.FPDL.FRA.EU [Laval] Z:53000  $:940105031141
> R:940106/2324Z @:F6DEG.FNOR.FRA.EU [Alen=87on] #:241473 Z:61000 FBB5.15
> R:940106/2256Z @:F6RAE.FNOR.FRA.EU [Vernon] #:257044 Z:27207 FBB5.15
> R:940106/2245Z @:F6RAC.FRPA.FRA.EU #:250033 [Paris - FBB5.13]
> R:940106/2226Z @:F6PTT.FRPA.FRA.EU #:64801 [91-MASSY] FBB5.15b $:94010503=
1141
> R:940106/2203Z @:F5MSQ.FCEN.FRA.EU [MUIDES] #:52239 Z:41500 FBB5.15
> R:940106/2132Z @:F8REF.FCEN.FRA.EU [Tours] #:44372 Z:37100 FBB5.15
> R:940106/2123Z @:F6KBN.FCEN.FRA.EU [St EPAIN] #:7992 Z:37320 FBB5.15
> R:940106/2114Z @:F5GHV.FPOC.FRA.EU [Poitiers] #:251561 Z:86000 $:94010503=
1141
> R:940106/2039Z @:F1HAQ.FALI.FRA.EU [Brive] #:280874 Z:JN05SD $:9401050311=
41
> R:940106/2037Z @:F6KDC.FALI.FRA.EU [Clermont-Fd]#:197037 JN15NQ $:9401050=
31141
> R:940106/2002Z @:F6BIG.FRHA.FRA.EU [Annecy (74)] #:399580 Z:74940 FBB5.15
> R:940106/1958Z @:HB9IAP.SROM.CHE.EU [GENEVE] #:232865 Z:1213 FBB5.15-I.A.=
P.C.
> R:940106/1937z @HB9PD.CHE.EU [PRIG BOX Bern, JN36RW, TheBox 1.9b]
> R:940106/0900z @HB9EAS.CHE.EU [The Basel Area BBS]
> R:940106/0903z @DB0GE.#SAR.DEU.EU [BBS Saarbruecken, DieBox 1.9]
> R:940106/0828z @ON4UBO.#LG.BEL.EU [Battice(LG),JO20VP,OP : ON4UAA]
> R:940106/0831Z @:ON1AEO.#DST.BEL.EU [Schaffen] #:11538 Z:3290 FBB5.15
> R:940106/0738Z @:ON6AR.#AN.BEL.EU [Antwerpen <PWG>] #:56442 Z:B-2000 FBB5=
.15
> R:940106/0622Z @:ON4AWP.OVN.BEL.EU [Gent, JO11ub] #:21208 Z:B-9000 FBB5.1=
5
> R:940106/0604Z @:PI8MID.#ZLD.NLD.EU [Middelburg] Z:4336XD $:940105031141
> R:940106/0450Z @:PI8VNW.#ZH2.NLD.EU [Hoek v Holland] #:6068 Op:PE0MAR
> R:940106/0208z @:PA0OKC.AMPR.ORG. [Z'meer] JNOS1.15 #:9845 $:940105031141=
 Z:2724 HR
>=20
> >From [e-mail] Thu Jan 06 02:08:49 1994
> Received: from duttnpc.tn.tudelft.nl by pa0okc.ampr.org. (JNOS1.15) with =
SMTP
> =09id AA9845 ; Thu, 06 Jan 94 02:08:16 UTC
> Received: from amsat.org by duttnpc.tn.tudelft.nl (JNOS1.10x1) with SMTP
> =09id AA20618 ; Wed, 05 Jan 94 04:58:02 UTC
> Received: from localhost by AMSAT.Org (8.6.4/amsat.1)
> =09id DAA04528 to ans-dist; Wed, 5 Jan 1994 03:16:50 GMT
> Received: from dub-img-2.compuserve.com by AMSAT.Org (8.6.4/amsat.1)
> =09id TAA04525 to <[e-mail]>; Tue, 4 Jan 1994 19:16:48 -0800
> Received: from localhost by dub-img-2.compuserve.com (8.6.4/5.930129sam)
> =09id WAA24248; Tue, 4 Jan 1994 22:14:21 -0500
> >From: Russ Platt WJ9F <[e-mail]>
> Message-ID: <[e-mail]>
>=20
> HR AMSAT NEWS SERVICE BULLETIN 001.04 FROM AMSAT HQ
> SILVER SPRING, MD January 1, 1994
> TO ALL RADIO AMATEURS BT
> BID: $ANS-001.04
>=20
> Recommended Operation Procedure to Reduce AO-16 Uplink Contention
>=20
> 1993 has brought many new satellites and many new satellite users.  I fee=
l
> it would be good to dust off an old bulletin from 1991 to help refresh
> the "old-timers" procedures and to aquaint new users to the recommended
> uplink frequency usage.
> The AO-16 Command Team recommends that users of the AO-16 PBBS system
> use only uplink channel D (145.960 Mhz) for download and directory reques=
ts
> leaving channels A, B, and C (145.900, 145.920, and 145.940 Mhz) for file
> uploads and digi users.
> Stations uploading files should stay off of the download/directory/fill
> request channel D as their longer uplink packets will collide with the
> shorter request packets.  Stations doing downloads and directories should
> stay off channels A, B, and C since their frequent but short requests wil=
l
> collide with longer uplink attempts seriously degrading uplink performanc=
e.
> Another benefit of using this procedure, while most of the uplink activit=
y
> to AO-16 will be on channel D (145.960) this frequency is high enough in =
the
> passband of AO-13 that QRMing our fellow operators will be kept to a minu=
mum
> when Pacsat crosses beneath AO-13's path.
>=20
> Recommended AO-16 operating practice in summary:
>=20
> Downlinks:   437.050 (also 2400.143 on experimenter's day.)
> Uplinks:     145.900 A  uploads
>              145.920 B  uploads
>              145.940 C  uploads
>              145.960 D  downloads, fills and directory requests
>=20
>=20
>  WJ9F /  AO-16 Command Team Leader=20
> =20
>=20
>=20
>=20

------------------------------

Date: 12 Jan 94 04:33:59 GMT
From: [e-mail]
Subject: ANS Bulletin 001.01
To: [e-mail]

On 2 Jan 1994 [e-mail]. wrote:

> R:940108/0939Z @:VK3BBS.VIC.AUS.OC #:12803 [St Albans] FBB5.15b $:940102210233
> R:940108/1042Z @:VK1KCM.ACT.AUS.OC [Canberra, ACT] $:940102210233
> R:940108/0902Z @:OH3RBR.#TRE.FIN.EU #:21426 [Tampere] FBB5.15b $:940102210233
> R:940107/2350Z @:OH6RBV.#VAA.FIN.EU #:54818 [Vaasa, KP03TC] FBB5.15b $:94010221
> R:940108/0120Z @:OH6RBG.FIN.EU [Jakobstad, KP13IQ] FBB5.14d #:131868
> R:940108/0012Z @:SK2AT.AC.SWE.EU [Umea, KP03DU] #:1985 Z:90742 FBB5.15
> R:940107/1748Z @:SM2TEZ.AC.SWE.EU [Umea] Z:90637 F5.15 $:940102210233
> R:940106/0833Z @:GB7BBS.#28.GBR.EU #:65319 [Bridgnorth] $:940102210233
> R:940106/0750Z @:GB7PMB.#28.GBR.EU [Minsterley] #:23800 Z:SY5 FBB5.15
> R:940106/0748Z 48638@GB7CHS.#11.GBR.EU [Cheshire NTS] $:940102210233
> R:940106/0739Z @:GB7SAM.#11.GBR.EU [Staffordshire] #:163675 $:940102210233
> R:940106/0742Z @:GB7MAX.#28.GBR.EU [IO82VO] $:940102210233
> R:940106/0550Z @:GB7COV.#29.GBR.EU [Coventry] FBB5.14 #:11970
> R:940106/0334Z @:GB7LWB.#27.GBR.EU [Northampton] #:78404 Z:NN7 1AE FBB5.15
> R:940106/0313Z @:M0DEM.#38.GBR.EU [London] #:116520 Z:IO90WX FBB5.15
> R:940106/0107Z @:GB7ICE.#34.GBR.EU [Rochester_Kent] #:13380 Z:ME2 FBB5.15
> R:940106/0027z 9502@GB7MXM.#36.GBR.EU $:940102210233 [Felixstowe:JO01PX] NNA V2.04
> R:940103/1042Z @:ON1CED.WVN.BEL.EU [Beernem] #:40768 Z:8720 FBB5.15
> R:940103/0941Z @:ON4AWP.OVN.BEL.EU [Gent, JO11ub] #:18743 Z:B-9000 FBB5.15
> R:940103/0930Z @:ON6AR.#AN.BEL.EU [Antwerpen <PWG>] #:53870 Z:B-2000 FBB5.15
> R:940103/0917Z @:ON1AEO.#DST.BEL.EU [Schaffen] #:9554 Z:3290 FBB5.15
> R:940103/0857z @ON4UBO.#LG.BEL.EU [Battice(LG),JO20VP,OP : ON4UAA]
> R:940103/0843z @DB0IZ.#NRW.DEU.EU [Solingen, JO31NE, Op: DL6EE]
> R:940103/0839z @DB0MKA.DEU.EU [MAILBOX KOELN-AACHEN, JO30PR OP: DL3OE]
> R:940103/0837z @DK0MWX.#NRW.DEU.EU [Langenfeld JO31LC, DL-HF 20m OP:DL1WX]
> R:940103/0820z @DB0SGL.DEU.EU [Brachbach, JO30XU, TheBox1.9a SYSOP: DC5KL]
> R:940103/0817z @DB0END.#NRW.DEU.EU [Ennepetal, JO31QH, TheBox 1.9 SYSOP: DB4DU]
> R:940103/0115Z @:PI8DAZ.#TWE.NLD.EU [Hengelo] $:940102210233
> R:940102/2341Z @:PI8DRE.#DRE.NLD.EU [Mailbox_Drenthe] #:292098 Z:9489TH FBB5.15
> R:940102/2155Z @:PI8APD.#GLD.NLD.EU [Apeldoorn] #:73927 Z:7327 AV FBB5.15
> R:940102/2201Z @:PI8PKT.#NH2.NLD.EU [Velserbroek] #:17769 Z:1991SP FBB5.15
> R:940102/2139Z @:PI8VNW.#ZH2.NLD.EU [Hoek v Holland] #:150509 Op:PE0MAR
> R:940102/2225z @:PA0OKC.AMPR.ORG. [Z'meer] JNOS1.15 #:9614 $:940102210233 Z:2724 HR
>
> >From [e-mail] Sun Jan 02 22:27:02 1994
> Received: from duttnpc.tn.tudelft.nl by pa0okc.ampr.org. (JNOS1.15) with SMTP
>     id AA9614 ; Sun, 02 Jan 94 22:25:57 UTC
> Received: from amsat.org by duttnpc.tn.tudelft.nl (JNOS1.10x1) with SMTP
>     id AA20488 ; Sun, 02 Jan 94 22:32:19 UTC
> Received: from localhost by AMSAT.Org (8.6.4/amsat.1)
>     id VAA03214 to ans-dist; Sun, 2 Jan 1994 21:08:01 GMT
> Received: from dub-img-2.compuserve.com by AMSAT.Org (8.6.4/amsat.1)
>     id NAA03211 to <[e-mail]>; Sun, 2 Jan 1994 13:07:58 -0800
> Received: from localhost by dub-img-2.compuserve.com (8.6.4/5.930129sam)
>     id QAA08990; Sun, 2 Jan 1994 16:05:32 -0500
> >From: Bill Tynan <[e-mail]>
> Message-ID: <[e-mail]>
>
> HR AMSAT NEWS SERVICE BULLETIN 001.01 FROM AMSAT HQ
> SILVER SPRING, MD January 1, 1994
> TO ALL RADIO AMATEURS BT
> BID: $ANS-001.01
>
> A number of messages have recently been posted to the AMSAT BBS
> concerning the schedules for the various satellites and how they
> are arrived at.  In the case of OSCAR-13, the schedule is
> determined by the AO-13 Command Team consisting of James Miller
> G3RUH, Peter Guelzow DB2OS and Graham Ratcliff VK5AGR.  As to how
> these volunteers determine the schedule, a very fine set of
> comments was posted by Paul Beckmann WA0RSE Internet address
> [e-mail].  The AMSAT News Service thanks Paul for his well-
> put comments and has taken the liberty of extracting them for this
> bulletin.
>
> Paul begins by asking himself: What determines the mode schedule
> for a satellite? He says thae he found an answer in the very
> clearly written piece in the 1993 Space Symposium Proceedings by,
> you guessed it, James, G3RUH.
>
> In his attempt to put the article by James in terms that may not be
> obvious to new to satellites as well as many not so new
> "bird-watchers", Paul offers a list of some of the important
> considerations:
>
> 1. All modern satellites are battery-powered with solar cell
> recharging systems. In order to work, the batteries must stay
> charged.
>
> 2. Most satellites do not have solar cells covering their entire
> surface.  This means the attitude of the satellite with relation to
> the sun must be managed to keep the batteries charged.
>
> 3. The antennas are fixed to the satellite, not steerable, and
> necessarily "go along for the ride" when accomplishing Item 2.)
>
> 4. Each mode involves a receiver, a transmitter, and a pair of
> antennas.  The receivers vary in sensitivity, the transmitters in
> power, and the antennas in gain and beamwidth.
>
> 5. Because of Item 3, the characteristics of item 4 allow
> transponder operation only in particular modes, when the distances
> and spacecraft attitudes are within certain limits.  For example,
> a narrowbeam antenna pointing away from the Earth will not support
> communications.  If a particular mode requires the use of that
> antenna, it would not do any good to place the satellite in that
> mode, no matter how badly it was desired.  To change the attitude
> of the spacecraft to point the antenna at the Earth could very well
> compromise solar cell illumination, hence battery charge, hence
> spacecraft operation - and possibly even its life expectancy.
>
> 6. Because some modes draw more power than others, the battery
> power must be budgeted. This also constrains how long the satellite
> can operate in any particular mode.
>
> Paul admits to possibly missing some other major points, but he
> believes that these demonstrate to him, at least, that the mode
> schedule on AO-13, or any other bird, is not a self-serving
> decision made by some "elite superclass" who treat the bird as a
> "toy", but are considered decisions, constrained by the physics of
> the orbit, solar cells, batteries, equipment aboard, antennas,
> etc., designed to offer the best long-term schedule of transponder
> operation and to further the state-of-the-art for the next birds'
> designs.
>
> WA0RSE strongly suggests reading the article by James in the
> Proceedings.  He says that he was amazed at the number of
> specialized programs that had been written, complete with graphical
> output, to aid in the decision-making process to keep the AO-13
> satellite operational.  He expressed his opinion that
> James, and others like him, should be thanked for bringing clear
> explanations like these to the rest of us and for fostering
> experimentation in modes that have proven to provide better two-way
> satellite communications for our fellow hams across the globe.
>
> Paul sums up his message by saying that we need everyone interested
> in AMSAT, with their opinions, tempers, passions, talents, and good
> humor.  He also wishes all a Happy New Year. Peace on Earth. Good
> will toward all.
>
> Information on ordering a copy of the Space Symposium Proceedings,
> which contains James Miller's article can be found on page 12 of
> the Nov/Dec AMSAT Journal.
>
>

------------------------------

Date: 12 Jan 94 04:33:40 GMT
From: [e-mail]
Subject: ANS Bulletin 001.01
To: [e-mail]

On 2 Jan 1994 [e-mail]. wrote:

> R:940108/0951z 54772@KE7KD.#NONEV.NV.USA.NOAM [RENO, NV.]
> R:940108/0939Z @:VK3BBS.VIC.AUS.OC #:12803 [St Albans] FBB5.15b $:940102210233
> R:940108/1042Z @:VK1KCM.ACT.AUS.OC [Canberra, ACT] $:940102210233
> R:940108/0902Z @:OH3RBR.#TRE.FIN.EU #:21426 [Tampere] FBB5.15b $:940102210233
> R:940107/2350Z @:OH6RBV.#VAA.FIN.EU #:54818 [Vaasa, KP03TC] FBB5.15b $:94010221
> R:940108/0120Z @:OH6RBG.FIN.EU [Jakobstad, KP13IQ] FBB5.14d #:131868
> R:940108/0012Z @:SK2AT.AC.SWE.EU [Umea, KP03DU] #:1985 Z:90742 FBB5.15
> R:940107/1748Z @:SM2TEZ.AC.SWE.EU [Umea] Z:90637 F5.15 $:940102210233
> R:940106/0833Z @:GB7BBS.#28.GBR.EU #:65319 [Bridgnorth] $:940102210233
> R:940106/0750Z @:GB7PMB.#28.GBR.EU [Minsterley] #:23800 Z:SY5 FBB5.15
> R:940106/0748Z 48638@GB7CHS.#11.GBR.EU [Cheshire NTS] $:940102210233
> R:940106/0739Z @:GB7SAM.#11.GBR.EU [Staffordshire] #:163675 $:940102210233
> R:940106/0742Z @:GB7MAX.#28.GBR.EU [IO82VO] $:940102210233
> R:940106/0550Z @:GB7COV.#29.GBR.EU [Coventry] FBB5.14 #:11970
> R:940106/0334Z @:GB7LWB.#27.GBR.EU [Northampton] #:78404 Z:NN7 1AE FBB5.15
> R:940106/0313Z @:M0DEM.#38.GBR.EU [London] #:116520 Z:IO90WX FBB5.15
> R:940106/0107Z @:GB7ICE.#34.GBR.EU [Rochester_Kent] #:13380 Z:ME2 FBB5.15
> R:940106/0027z 9502@GB7MXM.#36.GBR.EU $:940102210233 [Felixstowe:JO01PX] NNA V2.04
> R:940103/1042Z @:ON1CED.WVN.BEL.EU [Beernem] #:40768 Z:8720 FBB5.15
> R:940103/0941Z @:ON4AWP.OVN.BEL.EU [Gent, JO11ub] #:18743 Z:B-9000 FBB5.15
> R:940103/0930Z @:ON6AR.#AN.BEL.EU [Antwerpen <PWG>] #:53870 Z:B-2000 FBB5.15
> R:940103/0917Z @:ON1AEO.#DST.BEL.EU [Schaffen] #:9554 Z:3290 FBB5.15
> R:940103/0857z @ON4UBO.#LG.BEL.EU [Battice(LG),JO20VP,OP : ON4UAA]
> R:940103/0843z @DB0IZ.#NRW.DEU.EU [Solingen, JO31NE, Op: DL6EE]
> R:940103/0839z @DB0MKA.DEU.EU [MAILBOX KOELN-AACHEN, JO30PR OP: DL3OE]
> R:940103/0837z @DK0MWX.#NRW.DEU.EU [Langenfeld JO31LC, DL-HF 20m OP:DL1WX]
> R:940103/0820z @DB0SGL.DEU.EU [Brachbach, JO30XU, TheBox1.9a SYSOP: DC5KL]
> R:940103/0817z @DB0END.#NRW.DEU.EU [Ennepetal, JO31QH, TheBox 1.9 SYSOP: DB4DU]
> R:940103/0115Z @:PI8DAZ.#TWE.NLD.EU [Hengelo] $:940102210233
> R:940102/2341Z @:PI8DRE.#DRE.NLD.EU [Mailbox_Drenthe] #:292098 Z:9489TH FBB5.15
> R:940102/2155Z @:PI8APD.#GLD.NLD.EU [Apeldoorn] #:73927 Z:7327 AV FBB5.15
> R:940102/2201Z @:PI8PKT.#NH2.NLD.EU [Velserbroek] #:17769 Z:1991SP FBB5.15
> R:940102/2139Z @:PI8VNW.#ZH2.NLD.EU [Hoek v Holland] #:150509 Op:PE0MAR
> R:940102/2225z @:PA0OKC.AMPR.ORG. [Z'meer] JNOS1.15 #:9614 $:940102210233 Z:2724 HR
>
> >From [e-mail] Sun Jan 02 22:27:02 1994
> Received: from duttnpc.tn.tudelft.nl by pa0okc.ampr.org. (JNOS1.15) with SMTP
>     id AA9614 ; Sun, 02 Jan 94 22:25:57 UTC
> Received: from amsat.org by duttnpc.tn.tudelft.nl (JNOS1.10x1) with SMTP
>     id AA20488 ; Sun, 02 Jan 94 22:32:19 UTC
> Received: from localhost by AMSAT.Org (8.6.4/amsat.1)
>     id VAA03214 to ans-dist; Sun, 2 Jan 1994 21:08:01 GMT
> Received: from dub-img-2.compuserve.com by AMSAT.Org (8.6.4/amsat.1)
>     id NAA03211 to <[e-mail]>; Sun, 2 Jan 1994 13:07:58 -0800
> Received: from localhost by dub-img-2.compuserve.com (8.6.4/5.930129sam)
>     id QAA08990; Sun, 2 Jan 1994 16:05:32 -0500
> >From: Bill Tynan <[e-mail]>
> Message-ID: <[e-mail]>
>
> HR AMSAT NEWS SERVICE BULLETIN 001.01 FROM AMSAT HQ
> SILVER SPRING, MD January 1, 1994
> TO ALL RADIO AMATEURS BT
> BID: $ANS-001.01
>
> A number of messages have recently been posted to the AMSAT BBS
> concerning the schedules for the various satellites and how they
> are arrived at.  In the case of OSCAR-13, the schedule is
> determined by the AO-13 Command Team consisting of James Miller
> G3RUH, Peter Guelzow DB2OS and Graham Ratcliff VK5AGR.  As to how
> these volunteers determine the schedule, a very fine set of
> comments was posted by Paul Beckmann WA0RSE Internet address
> [e-mail].  The AMSAT News Service thanks Paul for his well-
> put comments and has taken the liberty of extracting them for this
> bulletin.
>
> Paul begins by asking himself: What determines the mode schedule
> for a satellite? He says thae he found an answer in the very
> clearly written piece in the 1993 Space Symposium Proceedings by,
> you guessed it, James, G3RUH.
>
> In his attempt to put the article by James in terms that may not be
> obvious to new to satellites as well as many not so new
> "bird-watchers", Paul offers a list of some of the important
> considerations:
>
> 1. All modern satellites are battery-powered with solar cell
> recharging systems. In order to work, the batteries must stay
> charged.
>
> 2. Most satellites do not have solar cells covering their entire
> surface.  This means the attitude of the satellite with relation to
> the sun must be managed to keep the batteries charged.
>
> 3. The antennas are fixed to the satellite, not steerable, and
> necessarily "go along for the ride" when accomplishing Item 2.)
>
> 4. Each mode involves a receiver, a transmitter, and a pair of
> antennas.  The receivers vary in sensitivity, the transmitters in
> power, and the antennas in gain and beamwidth.
>
> 5. Because of Item 3, the characteristics of item 4 allow
> transponder operation only in particular modes, when the distances
> and spacecraft attitudes are within certain limits.  For example,
> a narrowbeam antenna pointing away from the Earth will not support
> communications.  If a particular mode requires the use of that
> antenna, it would not do any good to place the satellite in that
> mode, no matter how badly it was desired.  To change the attitude
> of the spacecraft to point the antenna at the Earth could very well
> compromise solar cell illumination, hence battery charge, hence
> spacecraft operation - and possibly even its life expectancy.
>
> 6. Because some modes draw more power than others, the battery
> power must be budgeted. This also constrains how long the satellite
> can operate in any particular mode.
>
> Paul admits to possibly missing some other major points, but he
> believes that these demonstrate to him, at least, that the mode
> schedule on AO-13, or any other bird, is not a self-serving
> decision made by some "elite superclass" who treat the bird as a
> "toy", but are considered decisions, constrained by the physics of
> the orbit, solar cells, batteries, equipment aboard, antennas,
> etc., designed to offer the best long-term schedule of transponder
> operation and to further the state-of-the-art for the next birds'
> designs.
>
> WA0RSE strongly suggests reading the article by James in the
> Proceedings.  He says that he was amazed at the number of
> specialized programs that had been written, complete with graphical
> output, to aid in the decision-making process to keep the AO-13
> satellite operational.  He expressed his opinion that
> James, and others like him, should be thanked for bringing clear
> explanations like these to the rest of us and for fostering
> experimentation in modes that have proven to provide better two-way
> satellite communications for our fellow hams across the globe.
>
> Paul sums up his message by saying that we need everyone interested
> in AMSAT, with their opinions, tempers, passions, talents, and good
> humor.  He also wishes all a Happy New Year. Peace on Earth. Good
> will toward all.
>
> Information on ordering a copy of the Space Symposium Proceedings,
> which contains James Miller's article can be found on page 12 of
> the Nov/Dec AMSAT Journal.
>
>

------------------------------

Date: Tue, 11 Jan 1994 16:19:35
From: sdd.hp.com!usc!howland.reston.ans.net!usenet.ins.cwru.edu!ukma!harold.ca.uky.edu![e-mail]
Subject: CA HAM vs Sheriff/FCC Update?
To: [e-mail]

     Has anyone heard an update on the California ham who lost his HT over
calling for help on the local Sheriff's frequency during an emergency?
Monitoring Times had a short note on it this month and said the League has
appointed a lawyer to fight the FCC's ruling, but not much more.
---
Harold
[e-mail]

------------------------------

Date: 11 Jan 1994 20:19:52 GMT
From: ipxpress.aws.waii.com!ep130.wg2.waii.com!ep130.wg2.waii.com![e-mail]
Subject: Fm Broadcast
To: [e-mail]

In article <[e-mail]>, [e-mail] (Alan Bloom)
writes:
|> chris andersen ([e-mail]) wrote:
|> : Is it possible for a person with ham or modified ham set up to broadcast
|> : on the 88-108 Mhz area???
|>
|> None of the other respondents mentioned that it is perfectly legal to
|> broadcast on the FM broadcast band using very low power.  You can
|> buy "wireless microphones" and other devices with a range of a couple
|> hundred feet or so.
|>
|> AL N1AL
|>

Al you are correct, I did not mention low power. IF you use less then 100mw and
a antenna for less then 5' in length then I beleive that it is legal. I thought
that a higher power was implied though.

Mike KB5TOJ

------------------------------

Date: 11 Jan 1994 21:15:40 GMT
From: sdd.hp.com!vixen.cso.uiuc.edu!howland.reston.ans.net!agate!news.Brown.EDU!NewsWatcher![e-mail]
Subject: Ramsey kits not too good
To: [e-mail]

In article <[e-mail]>,
[e-mail] (Steve Bunis SE Southwest Chicago) wrote:

>
> Just to mix up the pot abit more -  Just talked with a local ham
> who bought and put together the Ramsey 2 meter amplifier kit.  He
> was on the air with it last night and sounded very good.  I asked
> him if he had run into any problems with construction, design etc.
> and he claimed it came up and worked the first time.  He was very
> happy with it.  His total cost (kit + case & misc.) came to just
> under $50.
>
> Now I understand that this design is much less complex than building
> a transceiver, but it sounds like you need to pick and choose which
> kits to buy, and which to avoid.

So I'll throw my two cents in. Having built a couple of things from
Hamtronics (a voice-ID board and a 70cm, 30W amp) I must say that the
voice-id'er was ok, but the amp absolutely sucked. Never never never buy
anything from Hamtronics in kit form. It's not worth the headache. Then
again, so is their pre-built stuff too.

Tony

--
== Tony Pelliccio, KD1NR
== [e-mail]
== Brown University Alumni & Development Computing Services
== Box 1908
== Providence, RI 02912
== [phone]

------------------------------

End of Info-Hams Digest V94 #28
******************************